Complete Guide to Test Automation: Techniques, Practices, and Patterns for Building and Maintaining Effective Software Projects by Arnon Axelrod

Author:Arnon Axelrod [Axelrod, Arnon]
Language: eng
Format: epub
Tags: computers, Languages, General, Programming
ISBN: 9781484238325
Google: FRVwDwAAQBAJ
Publisher: Apress
Published: 2018-09-22T23:51:17.593747+00:00

2.Add relevant diagnostic information to the test result.

While the tendency of most people is for the first option, I generally prefer to try the second option first, and only if it doesn’t help fall back to debugging. The reason I prefer the second option is that diagnostic information that I add to the test can serve me to investigate future failures as well. In particular, when a test fails during a CI or nightly build and cannot be reproduced on the environment of the automation developer, then debugging won’t help, while diagnostic information would. See the next chapter for more information about investigating failures.

So, the most basic diagnostic information that can help us identify this problem is a screenshot of the page at the moment of the failure. On the one hand, if we see the button in the screenshot, then it means that there’s a problem in the way we try to find it. If, on the other hand, we won’t see the button, then we’ll have to continue investigating further, but the screenshot will probably provide us with more hints regarding the problem. Listings 12-14 and 12-15 show the code we add to SantiyTests.cs and MVCForumClient.cs respectively in order to take the screenshot. Note that most of the code we add to SanityTests.cs is specific to MSTest, but you can do similar things in other unit testing frameworks too.public TestContext TestContext { get; set; }

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.